-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add systemd restart override #483
add systemd restart override #483
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/hold
Restart=always | ||
RestartSec=1 | ||
|
||
# disable rate limiting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why disabling the rate limiting?
I experienced problems because a service is restarting continuously but the check wasn´t able to detect it down , can this happen to us?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It starts in under a second, the default rate limit of 5 in 10s doesn't seem useful in the context of kind, if we can determine a better one for kind we should do that.
We have no checks for this, instead we're observing if the workloads are up.
kubelet and containerd are our only services.
/hold cancel |
/retest |
…-sigs#483) * Update installation.adoc with latest create cluster gcp * Update quick-start-guide.adoc with latest create cluster gcp * Update quick-start-guide.adoc with latest create cluster aws unmanaged * Update quick-start-guide.adoc with latest create cluster eks/aks * Change -Enabling workload cluster's to Enabling workload clusters in order to avoid doc bad view * Change -Enabling workload cluster's to Enabling workload clusters in order to avoid doc bad view -installation- * Do EN doc update
In case the service exits, we want to ensure that it restarts.
The ubuntu package currently has (appears to be very similar to upstream):
cc @Random-Liu, perhaps something else to push upstream at some point ...